---
title: Charmhub | Deploy COS configuration using Charmhub - The Open Operator Collection
description: Deploy the latest version of COS configuration as a Kubernetes Operator
  on any cloud. Push user (3rd-party) rules to COS charms.
url: https://charmhub.io/cos-configuration-k8s
---

# COS configuration

[Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

* [Canonical Observability](https://charmhub.io/publisher/observability "View all packages from Canonical Observability")

Platform:

3.0/stable rev112-3-g0c3b812

```
juju deploy cos-configuration-k8s --channel 3.0/stable
```

[Learn to deploy on juju >](https://juju.is/docs/juju/manage-applications)

[Read documentation](https://documentation.ubuntu.com/observability/latest/)

#### Contacts

* [Submit a bug](https://github.com/canonical/cos-configuration-k8s-operator/issues)

---

Share your thoughts on this charm with the community on discourse.

[Join the discussion](https://discourse.charmhub.io/)

#### Push user (3rd-party) rules to COS charms.

COS Configuration K8s is a Juju charm that syncs observability configurations — such as
Prometheus alert rules, Loki alert rules, Grafana dashboards, and SLO specifications — from
a Git repository and forwards them to the corresponding COS charms. It is a complementary
charm to the Canonical Observability Stack (COS):
https://documentation.ubuntu.com/observability

This charm enables an infrastructure-as-code workflow for observability, allowing operators
to manage alert rules and dashboards in version control and have them automatically applied
to the running stack.

Key features:

* Automatic synchronization of configurations from a Git repository using git-sync.
* Forwarding of Prometheus alert and recording rules, Loki alert rules, Grafana dashboards,
  and SLO specifications to their respective COS charms via Juju relations.
* Support for private repositories via SSH keys, including Juju secrets integration for
  secure key storage.
* Configurable paths within the repository for each type of configuration.
* Configurable branch, revision, and clone depth for fine-grained control over the sync.
* On-demand sync via the sync-now action, in addition to periodic automatic updates.